Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #57
This ensures that heading text isn't annotated twice on a markdown body.
Currently, when this extensions runs on GitHub Issues, heading text is annotated twice.
This happens because:
.markdown-bodyto uniquely identify a markdown body. For whatever reason, on GitHub Issues specifically,.markdown-bodygets set twice on the same markdown body (on different divs)..markdown-bodyand add annotations, we get back 2.markdown-bodyfor the same comment box. As a result, we end up with double annotations.This PR adds early return logic.